README.TXT File
       Visual Intercept Incident Management System, Version 1.0.3
          (C) Copyright Elsinore Technologies, Inc. 1996-97

This document decribes the release notes for version 1.0.3 of the Visual
Intercept Incident Management System.

The majority of the release notes for Elsinore Technologies' Visual
Intercept Incident Management System are in Windows Write format. There
are two files containing release information.

README.TXT
Contains release notes and important information about the Visual
Intercept Incident Management System.

INSTALL.WRI
Contains release notes and important information about installation of
the Visual Intercept Incident Management System.


                       Elsinore Technologies, Inc.
		       10555 Northwest Freeway Suite 206
		       Houston, TX 77092
		       Ph:  713.956.1221
		       FAX: 713.956.0889
		       Internet: support@elsitech.com
                       http://www.elsitech.com
                       ftp://ftp.elsitech.com/elsitech.com/public

------------------------------------------------------------------------
Known Issues at time of release:
Windows NT 4.0 - 
      During installation, Visual Intercept may install several ODBC
      drivers that are in use on machines running Windows NT 4.0. The 
      ODBC Installer Manager may complain that these ODBC drivers are in
      use. The appropriate response is to Ignore the messages.

Uninstalling Visual Intercept v1.0 - 
      If you are upgrading from Visual Intercept v1.00 to v1.03, we 
      recommend that you manually delete the Visual Intercept
      directories and then delete any references to Elsinore in the
      registry. We do not recomment using the v1.0 Uninstaller. Please
      contact our Support engineers if you have further questions.

Data Source Names (DSN) -
      If your DSN points to a location where the database no longer
      exists (e.g., you move the database but do not change the DSN),
      you may get two (2) logon dialog boxes before you can logon to
      Visual Intercept. In addition, when trying to print a report,
      Crystal Reports may cause the application to crash (because it
      continues to point to the original data source). The fix is to
      edit the DSN, via the ODBC Manager, to point to the correct
      location of the database.

Printing -
      Visual Intercept uses Crystal Reports as the print engine. As
      Crystal Reports is not thread safe, it is possible for Visual
      Intercept to, "hang" when printing multiple documents.

Moving/Renaming Projects -
      We are aware of some problems when moving and/or renaming
      projects. Although these problems do not result in any data
      loss, they are, nevertheless irritating. The workaround is as
      follows: Prior to any renaming and/or moving of projects, update
      and/or insert any and all Visual Intercept documents. After
      renaming and/or moving a project, re-fetch any related documents
      from the data source.